Repository navigation
docs: clarify what Beta means for the dbt v2 adapter - #775
Merged
Merged
Conversation
Replace the blanket "not production-ready" warning with a concrete statement: dbt Core 1.x is GA, dbt v2 is Beta with pending features tracked in the parity table, and GA depends on the next steps already on the page.
canbekley
reviewed
Nov 3, 2026
|
|
||
| <Warning> | ||
| **Not production-ready.** The ClickHouse adapter for dbt OSS and dbt v2, and the dbt platform connection, are not yet generally available (GA). Use them only in development or staging projects. | ||
| **Beta, not yet GA.** The ClickHouse adapter for dbt OSS and dbt v2 is in Beta, and the dbt platform connection is in Private Beta. The dbt Core 1.x adapter, `dbt-clickhouse`, is GA and supported for production use; nothing on this page changes that. |
Contributor
There was a problem hiding this comment.
even though we clarify the term in the table below and in the second sentence here, I'm wondering whether dbt OSS can be easily confused with dbt Core 1.x, and whether we can refer to both dbt OSS and dbt v2 as just being dbt v2? wdyt?
Contributor
There was a problem hiding this comment.
I feel like the clarification is what we need for the confusion things you mentioned.
For example mentioning both dbt OSS and dbt v2 can help people differentiate them, specially for these that may be interesting in keeping the use of open source.
Contributor
There was a problem hiding this comment.
makes sense. yes I agree, the warning should be clear enough now. lgtm!
koletzilla
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The "Not production-ready" warning on the dbt OSS / v2 / Platform page was being read as "do not use dbt with ClickHouse at all", including by prospects who are evaluating the GA Python adapter. This rewords the warning to state what is GA (dbt Core 1.x), what is Beta (the v2 adapter and the platform connection), what works in Beta, and points to the parity table for what is still pending instead of hard-coding a list that goes stale.
Docs-only change; no code or changelog entry, matching #739 and #744.
Note
Low Risk
Documentation-only wording on the dbt v2 Beta page; no product or adapter behavior changes.
Overview
The dbt OSS / v2 / Platform page replaces the blunt “Not production-ready” warning with a Beta, not yet GA callout that separates what is production-ready today (
dbt-clickhouseon dbt Core 1.x) from what is Beta (v2 adapter) or Private Beta (platform connection).The warning now defines Beta in terms of what already works (materializations, contracts, tests, Cloud coverage, integration suite) and defers the pending gap list to the existing v1 vs v2 parity section, plus guidance to try v2 in dev/staging and stay on 1.x in production when parity or GA guarantees matter.
The GA timeline blurb is softened from “coming soon” to noting coordination with dbt Labs and that the page will be updated when ready.
Reviewed by Cursor Bugbot for commit 05bf872. Bugbot is set up for automated code reviews on this repo. Configure here.